An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

大家好， 想请教一下是否有开发者遇到过类似情况，并愿意分享处理经验。 假设某 App 收到第三方发起的知识产权投诉（例如图片、字体、素材等相关内容）。 开发者收到投诉后已经： 完成内部核查； 删除或替换了被投诉内容； 发布整改版本； 当前 App 及相关线上服务中已无法访问被投诉内容。 但投诉方认为双方争议并未解决，并持续基于历史使用行为提出异议或再次发起投诉。 想了解大家是否遇到过类似情况： 开发者完成整改后，Apple 是否曾针对同一事项再次联系过你们？ Apple 是否要求过额外材料，例如整改说明、授权证明或其他补充文件？ 如果当前版本和线上服务已经无法访问被投诉内容，Apple 在后续处理中通常更关注哪些方面？ 有没有开发者遇到过已经完成整改，但仍然因为同一事项被进一步处理甚至下架的情况？ 对于这类已经完成整改、但双方仍存在历史争议的问题，Apple 后续通常是如何处理的？ 我理解每个案件情况不同，也理解 Apple 会根据个案进行评估。 这里只是希望了解其他开发者的实际处理经验，以便更好地理解 App Store 在知识产权投诉方面的一般处理方式。 感谢大家分享经验。

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

Our app submission has been in "Waiting for Review" status for 8 days after another 8 days before that with no review. Typical review time is 24–48 hours, so this appears to be stuck. We have not received any communication from App Review during this period and there are no outstanding items in App Store Connect. Could a member of the App Review team please check the status of this submission? App Name: Blingz App ID: 6759068218 Bundle ID: com.apperfun.hub Version: 1.39.1 Submission ID: 381c3dce-68f5-426b-b6de-807f513d370f Submission Date: Jun 13, 2026 Support Case ID: 102915835489 Thank you.

Hi everyone, I'm hoping someone from App Review (or anyone who's been through this) can help, because I'm a bit stuck. My app Mingle (Apple ID: 6770285096, Version 1.0.1) has been sitting in "Waiting for Review" for well over a week now. I first submitted at the start of June, and after it sat there for ~6 days with no movement at all, I figured something might be wrong, so I canceled and resubmitted. The new one has now been waiting since June 15 with the same silence: Submission ID: c919ad21-902a-4a3c-a6cc-a5fbd9f7e2b1 Every previous review of this app went through in under 48 hours, so this is really out of the ordinary. I've already opened a support request through Contact Us, but I haven't heard anything back yet. This is genuinely blocking me - I've been trying to get this release out since the beginning of the month and everything on my end is ready and waiting on the review. Is there anything I can do to move this along, or any reason a submission would get stuck like this? If anyone from App Review could take a look, or point me to the right channel, I'd really appreciate it.

Hello everyone, I’m reaching out for some guidance regarding App Store Guideline 3.1.3(c) and an issue we’re facing during the app review process. Here’s the situation: Our app is designed exclusively for organizations (e.g., businesses, schools, etc.) and is not intended for individual users, consumers, or families. Organizations purchase access to our services directly through our website, and we manually onboard them into the app. Individual users cannot register themselves or gain access to the app unless they are part of a pre-approved organization. However, during the app review process, we received the following feedback: We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase. We believe this is a misunderstanding because: Our app does not allow individual users or families to register or access the app. All purchases are made outside the App Store via our website, and only organizations can complete these transactions. We manually onboard organizations and their users – there is no way for individuals to sign up or pay for access within the app. We’ve already explained this to the App Review team in App Store Connect, but we’re still facing issues. Has anyone else experienced something similar? If so, how did you resolve it? Here’s what we’ve done so far: Clearly stated in the app description that the app is for organizations only. Ensured that individual users cannot register or pay for access within the app. We’d appreciate any advice or insights from the community on how to better communicate this to the App Review team or if there’s something we might be missing. Thank you in advance for your help! Best regards, Bashar

Hello, I don't understand why Apple states that app reviews typically take 48 hours. In my experience, it has never been completed within 48 hours. It is usually at least 6–7 days, and in some cases I have waited up to two weeks just to receive a response. Another issue is that they never seem to provide all the problems clearly at once. I wait for a response, they point out one issue, I fix it, then after another week or two they identify a different issue that was already present from the beginning. This makes the entire process extremely slow and frustrating. Is there any way to get a faster response from the review team? Has anyone else experienced similar issues with App Review? Thank you.

Hello, My app has been in “Waiting for Review” status since May 28. App ID: 1471317275 The app was transferred to my developer account about two months ago. Since the transfer, previous reviews were completed without any issue, and I have not received any message in the Resolution Center or any indication that something is wrong with this submission. I am not sure if the app transfer could have affected the review queue, but the current submission has now been waiting for an unusually long time. Could someone from Apple please advise what I should do in this situation? Should I continue waiting, contact App Review Support directly, or resubmit the build? Thank you for your help.

I am using CI/CD method to build my apps, i dont have xcode simulator, so I cannot produce 13'' screenshots And I have an ipad that is NOT 13'' what can I do? I am locked out from releasing on ipads?

Expedited review requested 24h ago but no response, missed launch date

Hi there, this is my first app, so please be gentle. I submitted it on 6/16 (3 days ago) and I saw somewhere that it took 24-48 hours to be reviewed, and I believe that's when the people I invited to test it would start getting their email invitations. It's still at "Waiting for Review" on the Test Flight tab. Is this the same as THE "app review"? Or is it some "mini-review" for Test Flight? Either way, when should I start following up?

Hello, I am reaching out regarding a critical review delay affecting Summer Rockz (App ID: 6763247379), a European festival discovery app. Version 2.0.0 has been in "Waiting for Review" since June 16, 2026 at 17:30 CET with no movement. Review history for v2.0.0: June 3 — Submitted for review June 4 — Rejected (Guideline 1.1) June 4 — Addressed and resubmitted same day June 16 — Rejected again (Guideline 1.1) June 16, 17:30 — All issues addressed and resubmitted Today, June 19 — Still "Waiting for Review", 3 days with no status change What I have already done: Submitted an Expedited Review request with a documented business justification (summer festival season, time-critical launch window) Opened multiple support tickets Responded in detail to both rejection notices via the Resolution Center Why this is urgent: Summer Rockz serves a seasonal audience tied to the European festival calendar. June and July are the peak months. Every day of delay directly impacts active users and partner festivals that depend on the app being live. The app has no unresolved guideline issues. Both rejection points were addressed immediately and documented in the Resolution Center. Could someone from the App Review team investigate whether this submission is stuck or flagged? I am not asking to bypass the process — I am asking for visibility on a submission that appears frozen with no review activity after 3 days. Thank you.

Hello everyone, my application has been stuck in the "Information Submitted" status of Apple's review process for several weeks now. The system shows "Thanks for providing additional information—it is currently processing and will be reviewed shortly," but there has been no progress. During this time, I cannot access App Store Connect, and payments may be delayed. This situation has continued for weeks, seriously affecting my development and operational plans. Has anyone experienced a similar situation? Are there any methods to contact Apple to expedite the process or understand the specific reason for the delay? What additional information should I provide to move the review process forward? Thank you for your suggestions and help! @Apple

Hi, My app The Gold Standard (shown as "TGS" on the home screen, Apple ID: 6755989671) is a first-time submission. It was submitted on 26 May 2026 and has been in "Waiting for Review" status ever since — now around 4 weeks with no movement. I have followed up with Developer Support twice by email since submitting, but have only received automated "we've received your request" replies, with no follow-up and no change in status. There are no messages, rejections, or unresolved issues showing in App Store Connect, and no action appears to be required from my side. Could the App Review team please take a look and let me know whether the submission is simply in the queue, or whether anything is needed from me to help it proceed? I'd be grateful for any update. Thank you.

Hello, My app has been stuck in "Waiting for Review" status for 8 days now (since June 11), well beyond the standard 24-48h window. This is a resubmission after addressing all issues from a previous rejection. I have already: Submitted an expedited review request (no response) Sent an email to App Review 3 days ago (no response) Submission ID: cd753837-a630-460f-9459-46881ef599cd Has anyone experienced similar delays recently? Any advice on how to get an update would be appreciated. Thank you.

Hi all, I'm launching my first iOS app (Capacitor/Next.js WebView wrapper) with two auto-renewable subscriptions via RevenueCat, and I'm stuck on a persistent issue across multiple App Store Review rejections. Setup: Bundle ID: no.skaren.app Two auto-renewable subscriptions: no.skaren.app.premium.monthly and no.skaren.app.premium.yearly, both in a single subscription group RevenueCat integrated via @revenuecat/purchases-capacitor App-Specific Shared Secret added to RevenueCat App Store Connect API key (with correct Key ID/Issuer ID) added to RevenueCat Paid Apps Agreement: Active Bundle ID in RevenueCat matches exactly RevenueCat API key in app code matches dashboard exactly The problem: On a physical device (TestFlight build, signed into Sandbox Apple ID), calling Purchases.getOfferings() always returns: {"current":null,"allKeys":[]} No errors are thrown — the offerings object is just empty. This happens consistently across multiple builds, after removing a conflicting limitsNavigationsToAppBoundDomains WebView restriction (which was separately causing a blank-screen bug, now fixed and confirmed working on-device). App Store Connect status: This is our first subscription submission ever. Both subscription products currently show "Developer Action Needed" status in App Store Connect (their localizations were rejected once for vague wording, fixed and resaved, but the products remain in this state). App Review's rejection message explicitly states: "Apple reviews In-App Purchase products in the sandbox and the In-App Purchase products do not need prior approval to function in review." However, our experience suggests otherwise — RevenueCat returns zero offerings, and App Review's own testers also report an "error message displayed on the subscription page" when attempting to test the IAP flow. Question: Is it actually true that subscriptions in "Developer Action Needed" / not-yet-approved status can still be fetched via StoreKit/RevenueCat during sandbox testing? Or does the first-ever subscription submission genuinely need to be approved (i.e., go through the review cycle once) before getOfferings() will return populated data? Has anyone encountered this exact "chicken-and-egg" situation, where the first IAP submission can't be tested until reviewed, but review fails because it can't be tested? Any insight into whether this is expected sandbox behavior for first-time subscription submissions, or whether there's a configuration issue I'm missing, would be hugely appreciated. Thanks!

The app is waiting for review since April 22 (nearly 2 months!) with no sensible outcome. The first review never happened I contacted support several times and after more than 40 days I just deleted the submission and created a new one which was quickly rejected on June 3 with the following reasons: The app contains hidden features. The app provides a limited user experience as it is not sufficiently different from a web browsing experience. The reasons do not reflect the reality and I explained why this fully native app, high performance app can't be considered as it provides a limited user experience nor does it contain any hidden features. I referred to the video and explained the tech stack that could falsely trigger any webview concerns. On June 9 I had a call with Apple representative. Before anything the representative suggested for me to do something else in life and not chase the outcome of the review (!). In the end of the meeting he suggested I submit the appeal and so I did right after the call. 30 minutes later I was contacted via mobile by the same representative and he asked to not submit the appeal as they might have a resolution for my review and should just resubmit the same version. I did as suggested and the app has been waiting for review ever since with no communication whatsoever. Does anyone else have similar experience? Anything I can do at all? Submission ID c37cc165-1f58-435a-a394-35fbbee787f8

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.